fix(cycle-scripts-es-webpack): Test can now be written in ES6 #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
npm test
for the package I'm modifyingnpm run commit
instead ofgit commit
ISSUES CLOSED: #14
REPLACES #13
Rationale: Instead of adding a babel config file in the template, having it copied over when create-cycle-app create an app, we just configure it temporary via package.json . Once we
take-off-training-wheels
we remove the config from the package.json and we copy on the root as.bablrc
file. In this way we can hide complexity away from the user, until the very moment he decide to do so.IMHO, create-cycle-app should always try to hide complexity and just don't make the user think. Especially for core flavors. So any configuration and setting should be handled by create-cycle-app as much as possible leaving the user with a super clean project structure to work on and focus on.
@geovanisouza92 @Widdershin what you think? If you are ok with it, feel free to close #13 in favor of this